Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
(Publisher: Macmillan Computer Publishing)
Author(s): David Schaer, et al
ISBN: 0672311283
Publication Date: 12/15/97

Three text-based log files are maintained automatically by NWCONV for the purposes of monitoring conversions. All three are available from the LOGVIEW applet after you perform a trial or actual migration:

•  ERROR.LOG: As the name implies, errors generated during the migration are recorded for administrative review. This option is excellent for zooming in on problems immediately after the process.

•  SUMMARY.LOG: A summary of the migration is recorded. Examples are the total number of groups migrated, total kilobytes of files transferred, and so on.

•  LOGFILE.LOG: Depending on the number of users and groups to be migrated and your logging level, this file can be very large or very small. It describes in painstaking detail every NetWare attribute with a Windows NT equivalent that was recognized by NWCONV. Because the LOGFILE.LOG provides more information than is functionally useful, it serves as support detail for the whole process.

12.10. Saving Migration Options

After specifying user and file options, you return to the Migration Tool for NetWare dialog box. Continue to add as many source and destination servers as you want, tailoring User, Group, and File Options where necessary. As shown in Figure 12.29, you can choose to save your configuration settings. Before continuing with a trial migration, it is a good idea to save your work.

Figure 12.29.  You can save your configuration for later use.

Migrating one NetWare 3.1x server at a time is highly recommended. This lets you spot errors in the migration process. Migrating one server at a time also eliminates the possibility of duplication snags. Take the time to run a trial migration after adding each server.

12.11. Starting the Trial Migration

After configuring User, Group, File, and Logging options, you are prepared to begin the migration. One of the more useful features of NWCONV is the capability to perform a harmless trial migration to isolate potential problems beforehand. It is recommended that you execute NWCONV using the trial migration feature several times until you address each error listed in the error log.

In the course of a trial migration, NWCONV reacts exactly as if it were a normal migration. The Converting dialog box shown in Figure 12.30 displays during the process, giving you real-time summaries of errors encountered, number of objects transferred, and total kilobytes of files copied.

Figure 12.30.  A migration in progress.

The Transfer Completed dialog box provides brief summary information about the migration (see Figure 12.31). Click the View Log Files button to view the *.LOG files inside the LOGVIEW applet (see Figure 12.32).

Figure 12.31.  The summary information of a completed trial migration.

Figure 12.32.  Three log files are created as the result of the trial migration.

12.12. Starting the Live Migration

You should perform trial migrations several times and review the log files before performing the actual migration. As the administrator, you should feel comfortable with the results of your trials before you proceed with the actual migration. After all, you are responsible for solving any serious migration problems.

Select the Start Migration button on the main Migration Tool for NetWare dialog box to begin the migration. The duration of the migration depends upon the number of servers selected, the number of users to be converted, and the total kilobytes of files to be transferred.

There are two particularly interesting consequences to using NWCONV that you should be aware of: All user and group object names are transferred in all uppercase letters; as you know, objects created in User Manager for Domains are usually generated in lowercase. Beyond being aesthetically unpleasing, all-uppercase usernames might have some significance in diverse computing environments. Deleting an imported username renders its SID obsolete in newly constructed Access Control Lists (ACLs) created when NetWare files were migrated, having some consequence for user and group permissions after migration. Again, thoroughness counts big in performing a successful migration from NetWare.

12.13. Lab

This lab will aid you in your learning by testing you on the information presented in this chapter, as well as by giving you exercises to hone your skills. You will find answers to the review questions in Appendix B, “Answers to Review Questions.”

12.13.1. Review Questions

Question 1

What must you install on a Windows NT server to let a user log on locally and access client/server applications installed on a Novell NetWare server? Choose all that apply. (See section 12.3.1.)

A.  File and Print Services for NetWare (FPNW)

B.  Gateway Services for NetWare (GSNW)

C.  Directory Service Manager for NetWare (DSMN)

D.  NWLink IPX/SPX protocol

Question 2

What must you install on a Windows NT server to let a user log on locally and access file and print services on a Novell NetWare server? (See section 12.2.2.)

A.  File and Print Services for NetWare (FPNW)

B.  Gateway Services for NetWare (GSNW)

C.  Directory Service Manager for NetWare (DSMN)

D.  NWLink IPX/SPX protocol

Question 3

What frame type does NWLink default to if no frame type is detected on an Ethernet network?

A.  802.2

B.  802.3

C.  Ethernet II

D.  SNAP

Question 4

When installing a Windows NT computer on an Ethernet network with existing NetWare 4.1 servers, what frame type should be used?

A.  802.2

B.  802.3

C.  Ethernet II

D.  SNAP

Question 5

What is the simplest explanation of what the Gateway Services for NetWare does at the network level?

A.  It converts SAP to RIP.

B.  It converts SMB to NCP.

C.  It converts NBF to IPX.

D.  It converts CNN to MTV.